Are developers fixing their own bugs?: Tracing bug-fixing and bug-seeding committers

This is the post-print version of the Article. The official published version can be accessed from the link below - Copyright @ 2011 IGI GlobalThe process of fixing software bugs plays a key role in the maintenance activities of a software project. Ideally, code ownership and responsibility should be enforced among developers working on the same artifacts, so that those introducing buggy code could also contribute to its fix. However, especially in FLOSS projects, this mechanism is not clearly understood: in particular, it is not known whether those contributors fixing a bug are the same introducing and seeding it in the first place. This paper analyzes the comm-central FLOSS project, which hosts part of the Thunderbird, SeaMonkey, Lightning extensions and Sunbird projects from the Mozilla community. The analysis is focused at the level of lines of code and it uses the information stored in the source code management system. The results of this study show that in 80% of the cases, the bug-fixing activity involves source code modified by at most two developers. It also emerges that the developers fixing the bug are only responsible for 3.5% of the previous modifications to the lines affected; this implies that the other developers making changes to those lines could have made that fix. In most of the cases the bug fixing process in comm-central is not carried out by the same developers than those who seeded the buggy code.This work has been partially funded by the European Commission, under the ALERT project (ICT-258098)

Outcomes after perioperative SARS-CoV-2 infection in patients with proximal femoral fractures: an international cohort study

Objectives Studies have demonstrated high rates of mortality in people with proximal femoral fracture and SARS-CoV-2, but there is limited published data on the factors that influence mortality for clinicians to make informed treatment decisions. This study aims to report the 30-day mortality associated with perioperative infection of patients undergoing surgery for proximal femoral fractures and to examine the factors that influence mortality in a multivariate analysis. Setting Prospective, international, multicentre, observational cohort study. Participants Patients undergoing any operation for a proximal femoral fracture from 1 February to 30 April 2020 and with perioperative SARS-CoV-2 infection (either 7 days prior or 30-day postoperative). Primary outcome 30-day mortality. Multivariate modelling was performed to identify factors associated with 30-day mortality. Results This study reports included 1063 patients from 174 hospitals in 19 countries. Overall 30-day mortality was 29.4% (313/1063). In an adjusted model, 30-day mortality was associated with male gender (OR 2.29, 95% CI 1.68 to 3.13, p80 years (OR 1.60, 95% CI 1.1 to 2.31, p=0.013), preoperative diagnosis of dementia (OR 1.57, 95% CI 1.15 to 2.16, p=0.005), kidney disease (OR 1.73, 95% CI 1.18 to 2.55, p=0.005) and congestive heart failure (OR 1.62, 95% CI 1.06 to 2.48, p=0.025). Mortality at 30 days was lower in patients with a preoperative diagnosis of SARS-CoV-2 (OR 0.6, 95% CI 0.6 (0.42 to 0.85), p=0.004). There was no difference in mortality in patients with an increase to delay in surgery (p=0.220) or type of anaesthetic given (p=0.787). Conclusions Patients undergoing surgery for a proximal femoral fracture with a perioperative infection of SARS-CoV-2 have a high rate of mortality. This study would support the need for providing these patients with individualised medical and anaesthetic care, including medical optimisation before theatre. Careful preoperative counselling is needed for those with a proximal femoral fracture and SARS-CoV-2, especially those in the highest risk groups. Trial registration number NCT0432364